[nrf noup] tests: crypto: Add ENTROPY_GENERATOR in overlays #3206
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add ENTROPY_GENERATOR=y in overlays for l series devices. This fixes an error where a trng source is not included in ncs.
I attempted to fix this without an ugly noup here: nrfconnect/sdk-nrf@8479106, but this causes regressions in
benchmarks.current_consumption.systemoff.grtc_wakeup
andtests/drivers/uart/uart_mix_fifo_poll/drivers.uart.uart_mix_poll_fifo
. The issue here is with the mismatch between how zephyr handles including the rng and how it is handled in NCS. In NCS the assumption is made that when required it is enabled explicitly, while in zephyr it is implicitly enabled as long as it exists in the device tree. In the L series the assumption is also made that rng will not be called inside an interrupt as it owns and uses its own mutexes. The easiest way to handle this then was with these overlays as a noup.